An operating system built around one job: keep what's yours — your traffic, your identity, your access to information — yours. Not a feature bolted onto something else. The whole point.
Privacy isn't something a government or a platform grants you. It's something you maintain — quietly, by default, in the parts of the system nobody thinks to check. The moment you stop maintaining it is usually the moment it's already gone.
These examples are arranged from the most restrictive environments to more targeted forms of control. This is a qualitative snapshot, not an official ranking: laws, enforcement and access can change quickly.
For current reporting, compare independent monitoring from Freedom House, OONI and Access Now rather than treating this list as a live index.
Three ways to reach a blocked destination. In every diagram the direct line is cut by the filter — the working route just refuses to look like something worth blocking. Pick a method to see how.
A single encrypted tunnel to a server sitting outside the filtered network. Your provider only sees traffic going to the VPN — not where it ultimately ends up. The VPN forwards you to the blocked destination and relays the answer back. Simple and fast, but everything rides on trusting that one server.
Traffic is wrapped in layers of encryption and bounced through three volunteer relays — guard, middle and exit. Each hop peels one layer, so no single relay knows both who you are and where you're going. The block at your edge never applies because, to your provider, you're only talking to the entry relay.
A closed, peer-to-peer network where every participant also routes traffic for others. Requests travel through short, one-way chains of peers — "garlic routing" bundles several messages together so patterns are hard to trace. There's no single exposed line for a filter to cut, and most services live inside the network itself.
Not marketing language — these are constraints the system is built around, not settings you have to remember to turn on.
Nothing phones home. No usage stats, no crash reports, no analytics pipeline hiding behind a "help us improve" toggle.
Nothing that matters to your privacy should have to be taken on faith. What the system does on the network should be something you — or anyone — can verify.
No sign-up, no email, no phone number to start using it. Access to a private, working internet connection shouldn't come with a registration form.
The system is designed to forget the session the moment it ends, unless you deliberately tell it to remember.
Your device shouldn't be trivially recognizable to a network, a router, or a browser just by showing up.
Persistent storage, when you want it, is encrypted with a key only you hold — not one held in escrow "for your convenience."
No inflated roadmap. Here's what actually runs right now, and what's being actively built on top of it.
Built without bundled telemetry or preinstalled black boxes — what's installed is what you asked for, nothing extra riding along.
Configured deliberately: it's clear which modules are active and why each one is there.
The system doesn't announce itself to every network it joins.
Traffic routed through the onion network and I2P without manual setup at the user level.
Boots with no trace on disk — the system doesn't remember the session after shutdown unless you say otherwise.
Reduces how recognizable your device is on a local network and in the browser.
An optional volume for anyone who needs data to survive between sessions — locked with a key only you know.
bypassOS currently exists as a working build on its author's own machine. The public source, build instructions, and a first bootable image will land here once it's actually ready for other people's hands — no promised dates, just an honest status.